Re: error message "column "oid" doesn"t exist"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C730DA.E0D9F727
Content-Type: multipart/alternative;
boundary="----_=_NextPart_002_01C730DA.E0D9F727"


------_=_NextPart_002_01C730DA.E0D9F727
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hmm. Well, I am opening the tables for editing. All of the tables have =
unique primary keys that can be referenced. Is there a flag or something =
I can set to prevent it from looking for oid?
=20
Thanks,
Erika

________________________________

From: Oberle, Martin [mailto:martin.oberle@winntec.de]=20
Sent: Wednesday, January 03, 2007 1:36 PM
To: Erika Marlow
Subject: AW: [ODBC] error message "column "oid" doesn't exist"


As far as I know the odbc driver uses the oid to identify the records =
when updating records.
The driver adds the column oid to the query when the driver thinks that =
records mjight be updated
in the future. The error should not occure whe you open the table =
"readonly".
=20
good luck
=20
martin
=20

-----Ursprüngliche Nachricht-----
Von: pgsql-odbc-owner@postgresql.org =
[mailto:pgsql-odbc-owner@postgresql.org]Im Auftrag von Erika Marlow
Gesendet: Dienstag, 2. Januar 2007 19:00
An: pgsql-odbc@postgresql.org
Betreff: Re: [ODBC] error message "column "oid" doesn't exist"
=09
=09
We are recieving the error message "column "oid" doesn't exist" from a =
series of ODBC calls via ADO in a Visual Basic application. The SQL =
statements are all "SELECT * FROM